home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr35
/
spitfire.zip
/
README.1ST
next >
Wrap
Text File
|
1993-04-24
|
8KB
|
174 lines
SPITFIRE Conversion From Version 2.1 To Version 2.5
The purpose of this file is to explain the process and provide step
by step instructions for updating an existing SPITFIRE Bulletin Board
System running version 2.1 to version 2.5.
IF YOU ARE SETTING UP SPITFIRE FOR THE FIRST TIME...DISREGARD THIS FILE...
IT IS INTENDED ONLY FOR THOSE WHO ARE UPGRADING AN EXISTING SYSTEM!
STEP ONE
--------
The first thing you will need to do is replace your existing SFMAIN.MNU,
SFFILE.MNU, SFMSG.MNU and SFSYSOP.MNU files by overwriting them with those
included in the SPITFIRE 2.5 package.
These must be replaced with the new SFMAIN.MNU, SFFILE.MNU, SFMSG.MNU
and SFSYSOP.MNU so to include the new features which are included in
Version 2.5. The SPITFIRE Door option has been added to the SFMAIN.MNU,
SFFILE.MNU and SFMSG.MNU. The capability for users to scroll through
messages non-stop has been added in the SFMSG.MNU. The SFSYSOP.MNU uses
different titles for features found in earlier versions of SPITFIRE.
Many of you may have individualized your menu selections and hesitate to
overwrite them, but it is ABSOLUTELY NECESSARY. Once you have adapted to
the Version 2.5, the menus can be modified as you did previously. You may
want to print out your existing menus before overwriting and then make
the adjustments on the new menus from your printout of your current menu
selections.
STEP TWO
--------
The next step will be to overwrite your existing SPITFIRE.EXE file and
your existing SPITFIRE.HLP files with those included in the SPITFIRE 2.5
package.
SPITFIRE.EXE contains numerous changes from the earlier version. The most
significant of those being the inclusion of the ability to include SPITFIRE
Doors in your systems operation and the capability to use External Protocol
File Transfers for uploading and downloading files to and from the BBS.
SPITFIRE.HLP has been modified to include explanations to the user for
the new features which have been incorporated within SPITFIRE Version 2.5.
STEP THREE
----------
The existing SF.BAT MUST be replaced with a new SF.BAT file which is
included in the SPITFIRE 2.5 package. The new SF.BAT handles instructions
that SPITFIRE sends it to execute the commands you enter to allow SPITFIRE
Door programs to run on your system.
BEFORE overwriting your existing SF.BAT file, either make a printout
or write down the contents of your current SF.BAT file. This is to insure
that any existing commands which are being used to begin SPITFIRE or run
scheduled events can transferred to the new SF.BAT file. Once you have
a copy of your existing SF.BAT file, overwrite it with the new SF.BAT
file that is included in the SPITFIRE 2.5 package.
Once the new SF.BAT is installed, enter all the necessary commands from
your previous SF.BAT file which may have you used to begin SPITFIRE or run
scheduled events on your BBS.
STEP FOUR
---------
The next step in the conversion process will be to run the SF21_25
utility. Several files in SPITFIRE Version 2.5 have been renamed for the
sake of conformity. The purpose for doing so was to enable Sysops to easier
identify the file category. All files which now end with a .BBS or a .CLR
are Display files. The files which have been changed are listed below. The
name of the file as it appears in Version 2.1 and earlier is on the left and
the revised name of the file as it appears in Version 2.5 is on the right.
SFUSERS .BBS --> SFUSERS .DAT
SFMSG .BBS --> SFMSG .DAT
SFMSGPTR.BBS --> SFMSG .PTR
SFBBSLST.BBS --> SFBBSLST.DAT
HEYSYSOP.BBS --> HEYSYSOP.LOG
DAILYLMT.BBS --> DAILYLMT.DAT
JOKER .BBS --> JOKER .DAT
SFEVENTS.BBS --> SFEVENTS.DAT
NUQ .BBS --> SFNEWU .QUE
NUA .BBS --> SFNEWU .ANS
SFMAINQ .BBS --> SFMAIN .QUE
SFMAINA .BBS --> SFMAIN .ANS
EDITORAL.BBS --> SFNWSLTR.BBS
This should help to alleviate some of the confusion regarding file types.
To assist you in converting your file names, the utility SF21_25 is included
in the SPITFIRE package and will rename all the files previously mentioned for
you. Simply put SF21_25 in the main SPITFIRE directory. SF21_25 must be
run from the same directory in which the SFSYSDAT.SYS file exists. Next type
SF21_25 at the DOS prompt to initiate its execution. If SFSYSDAT.SYS is not
found, SF21_25 will notify you the SFSYSDAT.SYS file was not found and that
the SF21_25 utility is halting its execution.
When SF21_25 is first started, a message will be displayed informing you
that this utility is designed to assist with your conversion from SPITFIRE
Version 2.1 to Version 2.5. It will also explain that if you are not
upgrading your system you should press the ESC key and the utility will be
terminated, otherwise press C to Continue with the conversion process.
The first file SF21_25 looks for is the SFUSERS.BBS file. It will
make some necessary changes to this file and rename it to SFUSERS.DAT. It
will then look for SFMSGPTR.BBS and rename it to SFMSG.PTR. If the file is
not found you will be informed the file was not found and be instructed that
the file must be renamed by hand. One by one, SF21_25 will make the following
file name conversions:
SFMSG .BBS --> SFMSG .DAT
SFBBSLST.BBS --> SFBBSLST.DAT
HEYSYSOP.BBS --> HEYSYSOP.LOG
DAILYLMT.BBS --> DAILYLMT.DAT
JOKER .BBS --> JOKER .DAT
SFEVENTS.BBS --> SFEVENTS.DAT
NUQ .BBS --> SFNEWU .QUE
NUA .BBS --> SFNEWU .ANS
SFMAINQ .BBS --> SFMAIN .QUE
SFMAINA .BBS --> SFMAIN .ANS
EDITORAL.BBS --> SFNWSLTR.BBS
SF21_25 informs you as each file is being renamed in the process of its
operation. If for any reason the file is not found, SF21_25 will inform you
the file was not found and instruct you that that particular file will need
to be renamed by hand.
STEP FOUR
---------
The DAILYLMT.BBS will automatically be converted to DAILYLMT.DAT when
running the SF21_25 utility. However, you will need to refer to the SPITFIRE
manual to modify the DAILYLMT.DAT file to include the new options which are
provided in Version 2.5 of SPITFIRE. DAILYLMT.DAT now allows the Sysop to set
the number of bytes a user can download per day, the number of files a user
can download per day and whether the Sysop wishes to have the SFRATIO.BBS/CLR
file displayed to the user if the daily download limits are exceeded. These
are all set according the the security level of the user. The SPITFIRE manual
provides explicit instructions for setting these parameters.
STEP FIVE
---------
It will be necessary for any existing [x].SEC files to be renamed by
hand. For instance, if you are running a 10.SEC file, it should be renamed
10SEC.BBS. If you are running a 25.SEC, it should be renamed to 25SEC.BBS,
etc. There is no way to know what various security level special messages
may be operating on the various systems so it will be necessary for these
to be renamed by hand. It is now possible to make color security messages
if you would like to do so. Simply make the color message and name it
[x]SEC.CLR where [x] is the security level of the users you wish to have the
message displayed to.
STEP SIX
--------
SPITFIRE is now ready to run. If you intend to include the SPITFIRE
Door feature or the use of the External Protocol file transfer option on
your BBS, refer to the manual for detailed instructions on how these are
installed. However, once this conversion process is completed, your system
is completely functional and ready for operation.